@mitu ok good to know, i'll blow everything away and start from scratch. i must have glazed over the part about it not being supported on a DE. Also i was never planning on using vnc for it and figutred it would never work, was just using it for troubleshooting and setting up other things unrelated to retropie, im just to lazy to switch the input on my monitor :P

thanks for the info to you both, much appreciated.

To bring this thread to its full conclusion I finally got round to modifying my copy of Gloom Deluxe.

I made an HD floppy disk image file and used Workbench to copy the contents of both disks to this file. I then modified the s/startup-sequence file to boot straight into the game without loading the setup program. I used ED from the AmigaDOS Shell to do this.

I now have a single disk version of Gloom Deluxe that works perfectly.

@pjft said in Few benefits To Overclocking the CPU on the Pi4?:

I had read that the 4k60 flag is supposed to increase the clock by ~10%

The 4k60 flag increases the GPU core freq from 500mhz to 550mhz. It shouldn't affect the CPU freq. I have gotten weird readings in the past where it reported much higher CPU frequencies than is possible. Im not sure what causes it, but I believe it's a false report.

On further investigation a number of CD32 game have this issue, sometimes requiring port 1 and sometimes port 0. Individual settings files looks like the solution.

Generally CD32 games like a CD32 pad in port 1. The following games are exceptions:

Fire + Ice CD32. Needs a joystick (not a pad) in port 1.
Seek and Destroy CD32. Needs a CD32 pad in port 0.

@mitu ... Will report back lol

Has anyone noticed that Ocarina of Time Master Quest has the slow menu bug that the Vanilla Ocarina of Time used to have on lr-mupen64plus-next? Weirdly though the gliden64.custom.ini and mupen64plus.ini file doesn't have Ocarina of Time specific settings

@macraem I have the same problem. Were you able to find any solution?

I reverted to an older fw. All is good. Protip, never buy vizio. They remove features. They removed chroma 4:4:4 in later fw updates and it screwed everything up.

@skylabin
REgret the above post. It was invalid. The same error came back.
Now I created cma=384M in /boot/firmware/cmdline.txt and now it seems to work.
Thanks for the post made earlier .
jpm

My apologies, next time I post I'll be sure to put in all that information.

However, on this particular problem, I realized what the issue was... I hate to admit this, but in trying to switch from composite input to RGB, I was selecting the wrong input on my PVM. I actually cannot believe that I was that stupid, hahaha... that was several hours of troubleshooting down the drain because I apparently couldn't be bothered to double-check that I was on the right input!

In any case, thanks for your reply, but I managed to figure my stupidity out on my own!

Hi,

this is what I've done over Raspbian

git clone --branch fkms_rpi4 --depth=1 --single-branch https://github.com/RetroPie/RetroPie-Setup.git
cd RetroPie-Setup
sudo ./retropie_setup.sh
Perform basic install
After Installation, exit and to start Emulationstation

Note that if you installed the Desktop version of Raspbian you can't launch Emulationstation from it. You have to quit the desktop or set your pi to start under console instead of GUI ( you can set this from raspi-config )

@bc320 I'm with you on this. With such a versatile machine like the Pi (any model) you don't know what you'll be using it some years into the future. Furthermore, Retropie runs on Linux which uses free memory to buffer I/O operations to speed up file access etc. You can see the memory allocation with the command free -h.

@Tim-s-up The retropie weekly dev builds are usable and nowhere near as buggy as lakka. For example, Lakka still crashes endlessly with the ozone theme since July. Also, retropie uses retroarch as well...

The Pi4 is not supported by RetroPie yet - either with the image(s) provided on the download page or through the manual installation (over Raspbian).